How to Set Up a Creative Intake Process

The end of "quick request" chaos: a structured intake system that catches every brief, scores every priority, and protects the team from the queue.

• Intake forms save creative teams up to six work weeks per year.
• Requests outside the form go to the back of the queue, not the front.
• Prioritization frameworks remove "who asks loudest" from the decision.

A creative ops lead opens her inbox on Monday. Twelve creative requests landed since Friday: three over email, five in Slack DMs, two in product team meetings she did not attend, one in a Teams comment, one verbally at the coffee machine. Each request is real. Each is described differently. Each assumes it is "quick." By Tuesday she has spent six hours just clarifying what people actually want, before any work has started. The team has shipped nothing this week.

This is what no intake process looks like. The team is not slow because the work is hard. The team is slow because every request arrives in a different shape, with different information, through a different channel, claiming a different priority. A creative intake process is the system that turns that chaos into a queue the team can actually run.

What an intake process actually does

A creative intake process is not a form. It is the full sequence from "someone wants something" to "the team is committed to delivering it" — capture, clarification, prioritization, approval, and assignment. The form is the entry point. The rest is the operating model that makes the form work.

Industry analysis of creative operations frames it directly: with a centralized intake process and standardized form, creative teams have all the relevant information needed to kick off a project and hit realistic deadlines. The reverse is also true. Without it, the team spends a third of its capacity translating ambiguous requests into actionable briefs.

The benchmark from teams that get this right is concrete. Benefit Cosmetics' creative team processes 50–60 work requests every month through a standardized intake form, eliminating back-and-forth communication and saving the team nearly six work weeks per year. That is a quarter of one full-time person, recovered from coordination overhead alone.

The six elements every intake process needs

A functioning creative intake process has six explicit components. Missing any one of them is what causes the system to leak.

Element 1 — A single intake form. Every request enters through one form. The form captures the minimum brief data the team needs to scope and prioritize: requester, deliverable type, audience, deadline, success metric, budget, brand context, dependencies. Optional sections appear conditionally based on deliverable type — a video request shows different fields than an email creative.

Element 2 — One-channel enforcement. Requests that arrive outside the form do not get rejected — they get redirected to the form. The Pedowitz Group's 2026 framework states it directly: make the intake form the only path for submitting work. Work that enters without a complete brief goes to the back of the queue, not the front. Without enforcement, the form becomes optional, and the chaos returns within a quarter.

Element 3 — A triage owner. One named person reviews every incoming request within a defined window — typically 24 to 48 hours. They check completeness, flag ambiguity, route to clarification or queue. Without a triage owner, requests sit in limbo and stakeholders escalate through back channels.

Element 4 — A prioritization framework. Every accepted request is scored against a documented framework. The most widely used in marketing teams is RICE — Reach, Impact, Confidence, Effort — which produces a numeric score for ranking. Simpler frameworks (ICE: Impact, Confidence, Effort) work for smaller teams. The point is not which framework. The point is that priority becomes a number derived from criteria, not an outcome of who asked loudest.

Element 5 — SLAs by request type. Each deliverable type carries a documented turnaround time. A landing page banner: three business days. A new video master: three weeks. A multi-market campaign: four to six weeks. SLAs make capacity planning possible and make "everything is urgent" claims testable. Without them, every request is treated as equally urgent — which means nothing actually is.

Element 6 — Visible queue and status. Every accepted request is visible: where it is in the workflow, who owns it, when it ships. Stakeholders stop following up because they can see the answer themselves. Triage stops being interrupted by "is mine done yet?" pings, which were the original chaos before the form existed.

The intake form itself

The form does the most of the heavy lifting. The fields below cover what most marketing teams need:

REQUESTER: name, role, team

DELIVERABLE TYPE: [controlled list]

PROJECT NAME: short identifier

DESCRIPTION: what the asset must accomplish

AUDIENCE: who it speaks to

DEADLINE: requested vs flexible

SUCCESS METRIC: how impact will be measured

BUDGET: if applicable

BRAND CONTEXT: relevant brand or campaign

DEPENDENCIES: other teams, prior assets, regulatory checks

ATTACHMENTS: references, source files, prior versions

Conditional fields appear based on the deliverable type — a video brief shows duration and aspect ratios, an email creative shows audience segment and subject line. The form should not exceed 12–15 fields total per request. Above that, requesters skip the form or abandon mid-submission.

Where most teams fail the intake

Three patterns kill most intake initiatives.

The first is launching without enforcement. The team builds the form, announces the new process, and accepts the first off-channel request "just this once" because a senior stakeholder asked nicely. Within two weeks, the form has become optional. Within a quarter, the team is back to chaos with an extra step.

The second is over-engineering the form. Some teams design intake forms with 30+ fields covering every possible scenario. Requesters give up. The team ends up with fewer requests through the form, more through Slack, and the form becomes the symbol of the failed initiative.

The third is skipping the SLA layer. The team accepts requests but commits to no turnaround time. Stakeholders cannot plan around the team because the team cannot tell them when work will ship. Without SLAs, the form captures requests but does not solve the coordination problem the team built it for.

Where workflow infrastructure makes intake real

An intake process only works if the form, the queue, the assignments, and the deliverables live in the same system the team works in. When the form is in one tool, the project queue in a second, the assets in a third, and the approvals in a fourth, the coordination cost the form was supposed to remove just moves downstream.

A creative operations platform that captures the intake form, the prioritization queue, the project assignment, and the asset history in one continuous environment is what closes the loop. MTM operates in this layer: keeping the request, the brief, the asset, and the approval state in the same workflow, so an intake form becomes the entry point to a system the team can actually run, not a form that creates more work to track separately.

What leaders should do next

Map every request that landed last week, including the off-channel ones. Count them. Count the channels. Count the clarification messages. The number is the size of the current coordination tax.

Build the intake form against the six elements above. Pilot it with one team or one request type before scaling. Enforce the one-channel rule from day one — the system breaks if exceptions are granted in week one.

The teams that ship more creative work in 2026 are not the ones with bigger teams. They are the ones whose Monday morning does not start with "what do they actually want?" because the form already answered the question.

FAQ

What is a creative intake process? A structured system for capturing, evaluating, prioritizing, and assigning incoming creative requests. The intake form is the entry point; the full process includes triage, prioritization, SLAs, and assignment.

Why is one channel enforcement so important? Because intake forms only work if they are the only way to request work. The moment exceptions are granted for off-channel requests, the form becomes optional, and the chaos returns within weeks.

Which prioritization framework should we use? RICE (Reach, Impact, Confidence, Effort) is the most common in marketing teams. ICE is simpler and works for smaller teams. The framework matters less than the discipline of scoring every request the same way.

How many fields should the intake form have? 12–15 maximum, with conditional fields that appear based on deliverable type. Above this, requesters skip or abandon the form.

What is the highest-impact element to implement first? The triage owner. Without one named person responsible for processing requests within 24–48 hours, the form captures requests but the team cannot move them forward, and the system collapses.

Sources

• Pedowitz Group — Utilization and Velocity Model for In-House Marketing (2026): https://www.pedowitzgroup.com/blog/utilization-and-velocity-model-for-in-house-marketing-2026
• Asana — How 3 World-Class Teams Streamline Creative Production at Scale (Benefit Cosmetics, Dr. Martens): https://asana.com/resources/creative-production-workflow-examples
• Asana — Project Intake Software to Manage Requests: https://asana.com/resources/project-intake-process
• Growth Method — How to Pick a Prioritisation Framework — RICE, ICE, PIE, PXL, HIPE: https://growthmethod.com/prioritisation-frameworks/
• Adobe Business — Creative Operations Management Guide: https://business.adobe.com/blog/basics/making-creative-work-that-matters-a-guide-to-creative-operations